fix(scheduling): honour dependsOnGroups declared by @BeforeGroups - #3433

Fix #2804

@BeforeGroups(value = "A", dependsOnGroups = "Z") had no effect on scheduling: the whole of group
A — configuration included — ran before group Z had started.

Supersedes #2025, which contributed a sample demonstrating the bug but no fix. The regression test
here keeps that scenario.

Why the dependency reached nothing

• @BeforeGroups/@AfterGroups methods are not nodes of the scheduling graph. They are pulled
  dynamically by ConfigInvoker.invokeBeforeGroupsConfigurations, keyed on the current test
  method's getGroups().
• MethodHelper.topologicalSort deliberately excludes group configuration methods from group
  dependency handling (anyConfigExceptGroupConfigs, added by Order for DependsOnGroups has changed after TestNg 7.4.0 #2664): it resolves a group against
  configuration methods of the same kind, where a group names test methods.
• DynamicGraphHelper.createDynamicGraph builds the run order from getGroupsDependedUpon() of the
  test methods only; it never saw the configuration methods.
• ConfigInvoker reads no dependsOn* at all — only m_beforegroupsFailures, keyed on group
  membership.

So the declared dependency was read by no scheduler.

What changed

DynamicGraphHelper now carries the dependency on the test methods of the group the configuration
runs before — the one place that is actually scheduled.

• The group a configuration runs before is matched by name, which is how
  ConfigurationGroupMethods.getBeforeGroupMethodsForGroup picks it at invocation time.
• The depended-upon group is matched by the same regex matcher the test methods' own
  dependsOnGroups uses, through the MethodGroupsHelper overload that answers empty rather than
  throwing: a @BeforeGroups naming a group with no method in the current <test> stays the no-op
  it has always been, rather than becoming a new TestNGException.
• The group → methods resolution is done once per <test> and memoised per distinct group name, so
  the added cost does not scale with the number of methods in the target group.
• A group the test method itself belongs to is skipped: making every member of a group depend on the
  others is a cycle, not a dependency. That exclusion asks the same expression that resolved the
  group, so dependsOnGroups = "Z.*" excludes a method in Z1 exactly as a plain name excludes a
  method in Z.

TestRunner.privateRun passes the @BeforeGroups map through, after intercept() so it is the
final one and before anything mutates it.

Deliberately out of scope

Skip-on-failure is unchanged. TestInvoker.checkDependencies decides skips from the test
method's own dependsOnGroups, so a failing Z now orders A after it without skipping it.
Widening that rule would newly skip tests in suites that pass today — a separate behavioural change
from the ordering bug this issue reports.

@AfterGroups(dependsOnGroups = ...) is left alone. It fires after the last method of its
group, so the only sound edge for it is the same all-of-A-after-all-of-Z one, which is stronger than
that annotation asks for and would reorder suites that pass today. The reasoning is written down
next to the code.

Test

test.beforegroups.issue2804.GroupDependencySample plus three methods on the existing
BeforeGroupsTest, and GroupPatternDependencySample for the pattern case — two methods belonging
to both the group the configuration runs before and a group the expression matches. Priorities make the natural ordering prefer A over Z, so only the declared
dependency can put Z first — deterministic in both directions. On master the run is
setUpA, a1, a2, z1, z2; with the fix it is z1, z2, setUpA, a1, a2. Asserted on completion order
via InvokedMethodNameListener, sequentially and under ParallelMode.METHODS.

./gradlew build is green: 0 failures, 0 errors across every module.

Summary by CodeRabbit

• Bug Fixes
  • Corrected @BeforeGroups dependency ordering in sequential and parallel execution.
  • Prevented pattern-based dependencies from creating self-dependencies.
  • Fixed HTML report layout and parameter display issues, including mutable data-provider values and null parameters.
  • Reports are now generated safely when parameter conversion fails.
• Improvements
  • Added precise test-run timestamp accessors; legacy date accessors are deprecated.
• Tests
  • Added coverage for group dependency ordering and pattern-based dependencies.